Motivation

• A recent route-precedence refactor allowed dynamic routes that include static infix/suffix segments (e.g. /:id/settings) to score lower than fully static routes (e.g. /users/settings), causing dynamic routes to be tried before static ones and shadow them.
• The intended semantics are that purely static routes always take priority over dynamic routes, so the scoring must guarantee static routes remain above dynamic ones.

Description

• Clamp dynamic route precedence so dynamic patterns cannot score <= 0 by forcing a minimum score of 1 for any route detected as dynamic in routePrecedence.
• This change preserves the existing relative ordering among dynamic and catch-all routes while ensuring purely static routes (score 0) always outrank any dynamic route.
• Added a focused regression test that asserts /users/settings (static) outranks /:id/settings (dynamic with static suffix) by importing and exercising routePrecedence in tests/routing.test.ts.
• Files changed: packages/vinext/src/routing/utils.ts and tests/routing.test.ts.

Testing

• Ran the targeted routing test suite with pnpm vitest run tests/routing.test.ts, which completed and passed the routing tests including the new regression test.
• Ran the single-test invocation pnpm vitest run tests/routing.test.ts -t "keeps fully static routes ahead", which also passed and validates the specific case.
• The fix is minimal and localized to the precedence calculation so it preserves existing behavior observed by the routing tests.

Codex Task